home *** CD-ROM | disk | FTP | other *** search
- Path: toad.stack.urc.tue.nl!not-for-mail
- From: jaco@stack.urc.tue.nl (Jaco Schoonen)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Too system friendly?
- Date: 3 Apr 1996 01:05:15 +0200
- Organization: MCGV Stack, Eindhoven University of Technology, the Netherlands.
- Message-ID: <4jsbrb$clt@toad.stack.urc.tue.nl>
- References: <4jpq5f$i9g@toad.stack.urc.tue.nl> <4js7lr$njd@taiwan.informatik.uni-rostock.de>
- NNTP-Posting-Host: toad.stack.urc.tue.nl
- X-Newsreader: TIN [version 1.2 PL2]
-
- Gunther Nikl (gnikl@informatik.uni-rostock.de) wrote:
- : Jaco Schoonen (jaco@stack.urc.tue.nl) wrote:
- : > the CPU. The only thing I do which has something to do with graphics is the
- : > WritePixelLine8(), but that's not supposed to change it's source-data is it?
-
- : I don't have the autodocs handy but I think WritePixelLine8() clears your
- : buffer.
-
- I do have them handy and they don't mention that the buffer is cleared. I
- checked it a little closer today and the buffer is indeed cleared. It's
- *only* cleared if I write to an aga/ecs screen. When writing to a
- CyberGraphX-screen, the contents of the buffer remain the same.
- This is what I expected after reading the documentation.
-
- If there's nothing to do about it, what are my options of fixing this?
- Copying the line I want to display to another buffer and writing that one?
- Or something nicer?
-
- Please help, cause it really sucks when the documented routines have
- undocumented features like clearing the buffer. How can one program
- according to the rules, if they don't mention crucial things like this?
-
- Oh well...
-
- --
- Jaco Schoonen
- (jaco@stack.urc.tue.nl)
-